Add a metadata field on AttachmentBase for integration-internal use cases#106
Merged
Add a metadata field on AttachmentBase for integration-internal use cases#106
AttachmentBase for integration-internal use cases#106Conversation
wilkes-oai
approved these changes
Jan 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a
metadatafield onImageAttachmentandFileAttachmentso that users can store attachment-specific integration-internal metadata w/o having to maintain a separate mapping.The ChatKitServer filters out this field for all responses, but any endpoints outside of ChatKitServer (e.g. direct upload endpoints) must filter the field out manually.